Q As noted in your Icebreaker this week, your assignment is to develop a technical brief for an upcoming project in which your department head will implement a standardized technical writing process in your company. In the Icebreaker, you worked with your classmates to build a comprehensive list of possible sources you can use to support your point of view. In the Discussion, you practiced summarizing, analyzing, and synthesizing that information. Now, you’re going to pull it together in a short document that helps you describe the upcoming project. Step 1: Review the Requirements Here is a reminder of the scenario about which you’re writing: You are part of the technical writing department of a software company, and your department employs 20 different writers, editors, and graphic designers. Your department head has been talking about how challenging it has been during the last several months to produce consistent documents within the department. Given that you recently learned about the technical writing process, you have some ideas about how to improve the consistency of the documents in your department. After you presented the memo to your department head, she decided to move forward with the project and has now asked you to lead a project team to implement a standardized writing process. The next step in the project is to write a technical brief that describes the project in more detail. Your department head will need to sign off on what you include in the brief before any actual work is completed on the project. The technical brief must include • a summary of the project, • the desired outcomes that will be achieved from project completion, • evidence that supports the project’s completion, • a summary of the key participants in and stakeholders of the project, and • a conclusion. At least three different credible sources should be cited in the evidence section of the technical brief. Step 2: Craft Your Technical Brief Write a short report consisting of at least seven complete paragraphs, but no more than nine. In total, your brief should not exceed two single-spaced pages. Include adequate information for your department head to see that you have successfully taken the lead on the project and have documented your high level plans effectively, but remember to write concisely. You should include section headings in your technical brief to ensure that you’re including all required information. Step 3: Submit Your Technical Brief Compose your work using a word processor (or other software as appropriate) and save it frequently to your computer. Be sure to check your work and correct any spelling or grammatical errors before you upload it. Your technical brief should be submitted as a Word document (.doc, .docx, or .rtf) or PDF. When you are ready to submit your work, click "Browse My Computer" and find your file. Once you have located your file, click "Open" and, if successful, the file name will be displayed under the Attached files heading. Scroll to the bottom of the page and click "Submit." This assignment uses Turnitin. This assignment is due Sunday by 11:59 pm ET. Evaluation The TECH200 Written Assignment Grading Rubric explains how you will be graded. This assignment is worth 5% of your final grade. Outcomes This activity assesses the following module outcomes: • M3-03: Summarize supporting material from various sources. (CO2, CO3, CO4, CO9, CO10) • M3-04: Effectively integrate evidence in specific technical communication contexts. (CO2, CO3, CO4, CO9, CO10) • M3-05: Create a technical brief for a given context or procedure. (CO2, CO3, CO4, CO6, CO7, CO9, CO10)